Message type mapping for packet traffic prioritization

ABSTRACT

Techniques that enable user plane data to be carried by control plane messages and still be correctly recognized and prioritized as user plane data in a packet network are provided. A base station of cellular network receives a message from a user equipment (UE). The base station transmits a packet based on the received message over a packet network to a control plane component of the cellular network. When the UE data includes user plane data, the base station sets a differentiated services code point (DSCP) marking of the packet so the packet is prioritized as user plane data in the packet network. When the received message does not include user plane data, the base station sets the DSCP marking of the packet so the packet is prioritized as control plane data.

BACKGROUND

Network and Communications technologies such as the 3rd GenerationPartnership Project (3GPP) employ protocols and interfaces betweennetwork nodes to have a separate control plane for carrying systemgenerated control data and a user plane for carrying data generated byuser applications. The control plane and the user plane have verydifferent characteristics, e.g. tolerance of error and delay, expectedbit rates, etc. Network nodes can use Differentiated Services Code Point(DSCP) marking embedded in IP packets to recognize different payloadtypes and prioritize the IP packets accordingly.

Narrow Band Internet of Things (NB-IoT) is a Low Power Wide Area Network(LPWAN) radio technology standard developed by 3GPP to enable a widerange of cellular devices and services. NB-IoT focuses specifically onindoor coverage, low cost, long battery life, and high connectiondensity. NB-IoT uses a subset of the specifications of the Long-TermEvolution (LTE) standard but limits the bandwidth to a single narrowbandof 200 kHz. For example, NB-IoT uses Orthogonal Frequency DivisionMultiplexing (OFDM) modulation for downlink communications and SingleCarrier Frequency Division Multiplexing Access (SC-FDMA) for uplinkcommunications. In NB-IoT, user plane data is carried by the controlplane, so the underlying packet network is unable to use the DSCPmarking used for the control plane to recognize if the packet network iscarrying signaling or NB-IoT user plane data.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures, in which the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIGS. 1a and 1b conceptually illustrate a base station settingDifferentiated Services Code Point (DSCP) for transmitting packets in acore network.

FIG. 2 illustrates components of the core network that uses the DSCPmarking to prioritize packet traffic.

FIG. 3 is a block diagram showing various components of an examplecomputing device implementing the base station that sets DSCP markingsaccording to message types.

FIG. 4 conceptually illustrates a flow diagram of an example processperformed by the base station to set DSCP markings according to messagetypes.

FIG. 5 is a block diagram showing various components of an examplecomputing device implementing a Mobility Management Element (MME) thatsets DSCP markings according to message types.

FIG. 6 conceptually illustrates a flow diagram of an example processperformed by the MME to set DSCP markings according to message types.

DETAILED DESCRIPTION

This disclosure is directed to systems and techniques that enable userplane data to be carried by control plane messages and still becorrectly recognized and prioritized as user plane data in a packetnetwork.

In some embodiments, a base station of a cellular network receives amessage from a user equipment (UE). The base station transmits a packetbased on the received message over a packet network to a control planecomponent of the cellular network. When a message type of the receivedmessage indicates that the message includes user plane data, the basestation sets a differentiated services code point (DSCP) marking of thepacket so the packet is prioritized as user plane data in the packetnetwork. When a message type of the received message indicates that themessage does not include user plane data, the base station sets the DSCPmarking so the packet is prioritized as control plane data. By settingthe DSCP marking based on the message type, the base station enables thepacket network to recognize user plane data embedded in control planemessages and to correctly prioritize the packet traffic from the basestation.

FIGS. 1a and 1b conceptually illustrate a base station 100 that setsDSCP markings for transmitting a message from a UE to a control planecomponent in a core network. The DSCP marking enables the user planedata carried by control plane messages to be appropriately prioritizedas user plane data in a packet network. As illustrated, the base station100 provides connectivity to a wireless local area network 106 tovarious UEs, including a UE 102. The wireless local area network 106provided by the base station 100 enables the UE 102 (and other UEs) tocommunicate with a core network 104.

The base station 100 is a base station or a hotspot of a wirelessnetwork. The base station 100 may be an Evolved Node B (eNodeB) of acellular network, such as an LTE network. The base station 100 alsosupports a Low Power Wide Area Network (LPWAN), such as the Narrow BandInternet of Things (NB-IoT).

The UE 102 may be a smart phone, a computer, a mobile device, or adevice that is capable of wireless communication. The UE 102 may also bea stationary device (a meter, a light, a household appliance, etc.) thatis part of an NB-IoT.

The core network 104 includes routers, switches, or other types of dataforwarding elements for conducting data traffic (e.g., packet traffic)between various network endpoints such as UEs, base stations, hotspots,and other types of computing resources. The core network 104 alsoprovides access to external networks such as the Internet. The corenetwork 104 may include components that provide services to thesubscribers of a cellular network as well as tracking positions of theUEs. The core network 104 may include a packet network, e.g., an EvolvedPacket Core (EPC) that interconnects different components belonging toan Evolved Packet System (EPS). EPC is a framework for providingconverged voice and data on a 4G LTE network. EPC unifies voice and dataon an Internet Protocol (IP) service architecture and voice is treatedas just another IP application. This allows operators to deploy andoperate one packet network for 2G, 3G, wireless local area network(WLAN), and fixed access such as Ethernet, DSL, cable, and fiber.

The UE 102 may communicate with the base station 100 by Non-AccessStratum (NAS) messages. NAS messages are control plane messages to andfrom control plane components of the core network 104. The control planemessages may include messages for EPS Mobility Management (EMM) and EPSSession Management (ESM).

As illustrated, the base station 100 relays different types of NASmessages between the UE 102 and a control plane component 108 of thecore network 104. Table 1 below is a list of message types for EMM.Table 2 below is a list of message types for ESM.

TABLE 1 Message Types for EPS Mobility Management (EMM) 01000001 Attachrequest 01000010 Attach accept 01000011 Attach complete 01000100 Attachreject 01000101 Detach request 01000110 Detach accept 01001000 Tackingarea update request 01001001 Tracking area update accept 01001010Tracking area update complete 01001011 Tracking area update reject01001100 Extend service request 01001101 Control plane service request01001110 Service reject 01001111 Service accept 01010000 GUTIreallocation command 01010001 GUTI reallocation complete 01010010Authentication request 01010011 Authentication response 01010100Authentication reject 01010101 Identity request 01010110 Identityresponse 01011101 Security mode command 01011110 Security mode complete01011111 Security mode reject 01100000 EMM status 01100001 EMMinformation 01100010 Downlink NAS transport 01100011 Uplink NAStransport 01100100 CS Service notification 01101000 Downlink generic NAStransport

TABLE 2 Message Types for EPS Session Management (EMS) 11000001 Activatedefault EPS bearer context request 11000010 Activate default EPS bearercontext accept 11000011 Activate default EPS bearer context reject11000101 Activate dedicated EPS bearer context request 11000110 Activatededicated EPS bearer context accept 11000111 Activate dedicated EPSbearer context reject 11001001 Modify EPS bearer context request11001010 Modify EPS bearer context accept 11001011 Modify EPS bearercontext reject 11001101 Deactivate EPS bearer context request 11001110Deactivate EPS bearer context accept 11010000 PDN connectivity request11010001 PDN connectivity reject 11010010 PDN disconnect request11010011 PDN disconnect reject 11010100 Bearer resource allocationrequest 11010101 Bearer resource allocation reject 11010110 Bearerresource modification request 11010111 Bearer resource modificationreject 11011001 ESM information request 11011010 ESM informationresponse 11011011 Notification 11011100 ESM dummy message 11101000 ESMstatus 11101001 Remote UE report 11101010 Remote UE report response11101011 ESM data transport

Upon receiving an NAS message with an EMM (Table 1) or ESM (Table 2)message type, the base station 100 transmits a packet to the controlplane component 108. When relaying NAS messages between the UE 102 andthe control plane component 108, the base station 100 maps differentmessage types to different DSCP markings in packet headers. The packetnetwork of the core network 104 may in turn use the DSCP markings toprioritize the delivery of the packets. Specifically, when the messagetype indicates that the content of the message includes user plane data,the base station sets the DSCP marking to indicate user plane data. Anexample message type for user plane data is message type “11101011” or“ESM data transport”, which is a user data transport that carries userplane data between the control plane component 108 and the base station100. On the other hand, when the message type is one of the otherpossible values of EPS Mobility Management or EPS Mobility Managementsession as shown in Table 1 or Table 2, the base station 100 sets theDSCP marking to indicate control plane data.

FIG. 1a illustrates the base station 100 setting the DSCP markings whenthe message type of the NAS message 110 is “11101011” or “ESM datatransport”. The message type “ESM data transport” indicates that thecontent of the NAS message is user plane data rather than control planedata. Upon receiving the NAS message 110, the base station 100 sends thecontent of the NAS message 110 in a packet 112 to the control planecomponent 108. The DSCP marking of the packet 112 is set to a value “15”in this example, which is a value assigned to certain types of userplane data packets. The core network 104 correspondingly prioritizes thedelivery of the packet 112 based on the DSCP marking (e.g., lowerlatency, higher drop probability).

FIG. 1b illustrates the base station 100 setting the DSCP markings whenthe message type of the NAS message 114 is “01000001” or “AttachRequest”. The message type “Attach Request” indicates that the contentof the NAS message is control plane data. Upon receiving the NAS message114, the base station sends the content of the NAS message in a packet116 to the control plane component 108. The DSCP marking of the packet116 is set to a value “48” in this example, which is a value assigned tocertain types of control plane data packets. The core network 104correspondingly prioritizes the delivery of the packet 116 based on theDSCP marking (e.g., higher latency, lower drop probability).

FIG. 2 illustrates components of the core network 104 that use the DSCPmarking to prioritize packet traffic from the base station 100. The corenetwork 104 includes an LTE EPC, which includes several components suchas a Mobility Management Entity (MME) 200, a Serving Gateway (S-GW) 202,a Packet Data Node Gateway (P-GW) 204, and other components (notillustrated). The base station 100 is connected to the S-GW 202 througha S1-U interface and the MME 200 through a S11-MME interface. The MME isconnected to the S-GW 202 through an S11 interface. The S-GW 202 isconnected to the P-GW 204 through a S5 or S8 interface.

The MME 200 is a control plane component that manages session states andauthenticates and tracks a user across the cellular network. The MMEretains location information at the tracking area level for thesubscribing UEs of the cellular network, such as the UE 102. The MME isalso responsible for part of the handover signaling between LTE and2G/3G/5G networks.

The S-GW 202 resides in the user plane where it forwards and routespackets between the eNodeB base stations (e.g., the base station 100)and the P-GW 204. The P-GW 204 acts as the interface between the LTEnetwork and other packet data networks and manages quality of service(QoS) and provides deep packet inspection (DPI).

The MME 200 may forward some of the data that it receives from the basestation 100 to the S-GW 202. The base station 100 may also directlycommunicate user plane data to the S-GW 202 through the S1-U interface.Some of the data communicated to the S-GW 202 is in packets with userplane DSCP markings. The S-GW 202 forwards the received packets to theP-GW 204 through the S5 or S8 interface into a Packet Data Network(PDN), such as the Internet.

The base station 100 receives NAS messages from the UE 102. An NASmessage may include ESM or EMM data destined for the MME 200. Uponreceiving the NAS messages, the base station 100 transmits packets basedon the ESM or EMM data to the MME 200 through an S1-MME interface. Thebase station 100 inserts a DSCP marking based on the message type. Forexample, if the message type is a type of user plane data transport,e.g., “ESM data transport”, the base station 100 would set the DSCPmarking to a user plane DSCP. Otherwise, the DSCP marking would be setto a control plane DSCP.

Example Base Station

FIG. 3 is a block diagram showing various components of an examplecomputing device 300 implementing the base station 100 that sets DSCPmarkings according to message types. The base station computing device300 may be a general-purpose computer, such as a desktop computer,tablet computer, laptop computer, or any type of server that is capableof receiving inputs, processing the inputs, and generating output data.The computing device 300 may also be a virtual computing device in theform of virtual machines or software containers that are hosted in acloud.

The computing device 300 may be equipped with a communications interface302, one or more processors 304, device hardware 306, and memory 308.The communications interface 302 may include wireless and/or wiredcommunications components that enable the computing devices to transmitdata to and receive data from other devices, whether through a dedicatedwired connection or via a communications network. The device hardware306 may include additional hardware that performs user interface, datadisplay, data communication, data storage, and/or other serverfunctions.

The memory 308 may be implemented using computer-readable medium, suchas a computer storage medium. Computer-readable medium includes, atleast, two types of computer-readable media, namely computer storagemedia and communications media. Computer storage media may includevolatile and non-volatile, removable and non-removable media implementedin any method or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media may include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other non-transitory medium that can be used tostore information for access by a computing device. In contrast,communications media may embody computer-readable instructions, datastructures, program modules, or other data in a modulated data signal,such as a carrier wave, or other transmission mechanism.

The processor(s) 304 and the memory 308 of the computing devices 300 mayimplement an operating system 310, a UE interface 312, an MME interface314, and a gateway interface 316. The operating system 310 may includecomponents that enable the computing devices 300 to receive and transmitdata via various interfaces (e.g., user controls, communicationsinterface, and/or memory input/output devices), as well as process datausing the processors 304 to generate output. The operating system 310may include a presentation component that presents the output (e.g.,display the data on an electronic display, store the data in memory,transmit the data to another electronic device, etc.). Additionally, theoperating system 310 may include other components that perform variousadditional functions generally associated with an operating system.

The UE interface 312 is a software component that is responsible forreceiving data from and sending data to UEs through a wireless network.The UE interface 312 may exchange data with a UE through a radio accessnetwork of a cellular network. The UE interface 312 may also exchangedata with a UE through LPWAN or NB-IoT. The UE interface also examinesthe message types of the uplink messages (e.g., NAS messages) from theUE to determine whether the messages are for the MME (such as ESM or EMMmessages). Messages that are destined for the MME are handled by the MMEinterface 314. Messages that are not destined for the MME are handled bythe gateway interface 316.

The MME interface 314 is a software component that is responsible forexchanging control plane data with the MME 200, which is a control planecomponent. The MME interface 314 transmit packets to the MME based oncontent of the messages received from the UE interface 312. The MMEinterface 314 also sets the DSCP markings of the transmitted packetsbased on the message types of the received messages. For example, whenthe message type indicates “ESM data transport”, the MME interface 314would set the DSCP marking to a user plane DSCP value. In someembodiments, the MME interface 314 communicates with the MME byoperating an S1-MME interface.

The gateway interface 316 is a software component that is responsiblefor communicating user plane data with the S-GW 202, which is a userplane component. In some embodiments, the gateway interface 316communicates with the S-GW 202 by operating an S1-U interface.

FIG. 4 conceptually illustrates a flow diagram of an example process 400performed by the base station 100 to set DSCP markings according tomessage types. The base station relays uplink messages from UEs to theMME of the core network and inserts DSCP markings into packets based onthe message types of the uplink messages. The process 400 is illustratedas a collection of blocks in a logical flow chart, which represents asequence of operations that can be implemented in hardware, software, ora combination thereof. In the context of software, the blocks representcomputer-executable instructions that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions may include routines, programs,objects, components, data structures, and the like, that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the process.

At block 402, the base station receives an ESM or EMM message. The basestation may receive the ESM or EMM message from a UE as an NAS message.The base station may determine whether the NAS message is an ESM or anEMM message by examining the message type of the message.

At block 404, the base station generates a packet destined for the MMEbased on the content of the ESM or the EMM messages. At block 406, thebase station determines whether the message contains user plane data.For example, the base station may determine that the message containsuser plane data when the message type of the message indicates that themessage is an ESM data transport message. Thus, if the message typeindicates user plane data, the process proceeds to block 408. Otherwise,the process proceeds to block 410.

At block 408, the base station sets the DSCP marking of the packet to avalue for user plane data, which prioritizes the delivery of the packetas a user plane packet. The process then proceeds to block 412.

At block 410, the base station sets the DSCP marking of the packet to avalue for control plane data, which prioritizes the delivery of thepacket as a control plane packet. The process then proceeds to block412.

At block 412, the base station transmits the packet to the MME through apacket network. The DSCP marking is used by the packet network toprioritize the delivery of the transmitted packet.

Example WE

As mentioned above, for uplink EMM or ESM messages from the UE 102 tothe MME 200, the base station 100 inserts the DSCP marking based onmessage type.

In some embodiments, for downlink EMM and ESM messages from the MME 200to the UE 102, the MME 200 inserts the DSCP marking based on messagetype.

FIG. 5 is a block diagram showing various components of an examplecomputing device 500 implementing the MME 200, which sets DSCP markingsaccording to message types. The MME computing device 500 may be ageneral-purpose computer, such as a desktop computer, tablet computer,laptop computer, server, or other electronic devices that are capable ofreceiving inputs, processing the inputs, and generating output data. Thecomputing device 500 may also be a virtual computing device in the formof virtual machines or software containers that are hosted in a cloud.

The computing device 500 may be equipped with a communications interface502, one or more processors 504, device hardware 506, and memory 508.The communications interface 502 may include wireless and/or wiredcommunications components that enable the computing devices to transmitdata to and receive data from other devices, whether through a dedicatedwired connection or via a communications network. The device hardware506 may include additional hardware that performs user interface, datadisplay, data communication, data storage, and/or other serverfunctions.

The memory 508 may be implemented using computer-readable medium, suchas computer storage medium. Computer-readable medium includes, at least,two types of computer-readable media, namely computer storage media andcommunications media. Computer storage media may include volatile andnon-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules, orother data. Computer storage media may include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other non-transmission medium that can be usedto store information for access by a computing device. In contrast,communications media may embody computer-readable instructions, datastructures, program modules, or other data in a modulated data signal,such as a carrier wave, or other transmission mechanisms.

The processor(s) 504 and the memory 508 of the computing devices 500 mayimplement an operating system 510, an EPS mobility management module512, an EPS session management module 514, and a gateway interface 516.The operating system 510 may include components that enable thecomputing devices 500 to receive and transmit data via variousinterfaces (e.g., user controls, communications interface, and/or memoryinput/output devices), as well as process data using the processor(s)504 to generate output. The operating system 510 may include apresentation component that presents the output (e.g., display the dataon an electronic display, store the data in memory, transmit the data toanother electronic device, etc.). Additionally, the operating system 510may include other components that perform various additional functionsgenerally associated with an operating system.

The mobility management module 512 is a software component that isresponsible for tracking the location of UEs and for part of thehandover signaling between LTE and 2G/3G/5G networks. The mobilitymanagement module 512 is also responsible for handling EMM messages withUEs through base stations. The mobility management module 512 receivesand transmits messages with base stations through the S1-MME interface.The mobility management module 512 also sets the DSCP marking forpackets headed to base stations and UEs.

The session management module 514 is a software component that isresponsible for initiating paging and authentication of subscribing UEs.The session management module 514 is also responsible for handling ESMmessages with UEs through base stations. The mobility management module512 receives and transmits ESM messages with base stations through theS1-MME interface. The mobility management module 512 also sets the DSCPmarking for packets headed to base stations and UEs. For example, theDSCP marking is set to a user plane value when the message typeindicates “ESM data transport”.

The gateway interface 516 is a software component that is responsiblefor communicating with a gateway element of the core network, such asthe S-GW 202 or the P-GW 204. In some embodiments, the gateway interface516 communicates with the S-GW 202 by operating an S1-U interface. Insome embodiments, that base station may send user plane data embedded inESM or EMM messages to a gateway element.

FIG. 6 conceptually illustrates a flow diagram of an example process 600performed by the MME 200, which sets DSCP markings according to messagetypes. The MME 200 may send downlink messages to UEs through basestations and insert DSCP markings into packets based on the messagetypes of the downlink messages.

The process 600 is illustrated as a collection of blocks in a logicalflow chart, which represents a sequence of operations that can beimplemented in hardware, software, or a combination thereof. In thecontext of software, the blocks represent computer-executableinstructions that, when executed by one or more processors, perform therecited operations. Generally, computer-executable instructions mayinclude routines, programs, objects, components, data structures, andthe like, that perform particular functions or implement particularabstract data types. The order in which the operations are described isnot intended to be construed as a limitation, and any number of thedescribed blocks can be combined in any order and/or in parallel toimplement the process.

At block 602, the MME 200 generates or receives a message destined for aUE. The message may be an ESM message or an EEM message. At block 604,the MME 200 generates a packet based on the content of the EEM or ESMmessage.

At block 606, the MME 200 determines whether the message contains userplane data, for example, by examining whether the message type is “ESMdata transport”. If the message type indicates user plane data (such aswhen the message type is “ESM data transport”), the process proceeds toblock 608. Otherwise, the process proceeds to block 610.

At block 608, the MME 200 sets the DSCP marking of the packet to a valuefor user plane data, which prioritizes the delivery of the packet as auser plane packet. The process then proceeds to block 612 to transmitthe packet to a base station through the packet network.

At block 610, the MME 200 sets the DSCP marking of the packet to a valuefor control plane data, which prioritizes the delivery of the packet asa control plane packet. The process then proceeds to block 612 totransmit the packet to the MME through the packet network.

At block 612, the MME transmits the packet to a base station through apacket network. The DSCP marking is used by the packet network toprioritize the delivery of the transmitted packet.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. A computing device comprising: one or moreprocessors; and a non-transitory computer-readable medium storing aplurality of computer-executable instructions that are executable by theone or more processors to perform a plurality of actions, the pluralityof actions comprising: receiving, at a base station of a cellularnetwork, a non-access stratum (NAS) message from a user equipment (UE);determining, at the base station, that a message type of the NAS messageis an evolved packet system session management (ESM) data transport thatcarries user plane data; based on determining that the message type ofthe NAS message is the ESM data transport that carries user plane data,generating, at the base station, a packet that includes at least aportion of the NAS message; based on determining that the message typeof the NAS message is the ESM data transport that carries user planedata, setting, at the base station, a Differentiated Services Code Point(DSCP) marking of the packet that indicates the packet includes theportion of NAS message that is the ESM data transport that carries userplane data; and transmitting, by the base station, the packet thatincludes the DSCP marking that indicates the packet includes the portionof NAS message that is the ESM data transport that carries user planedata and that indicates a priority of the packet over a packet networkto a mobility management element (MME) of the cellular network thatauthenticates UEs in the cellular network.
 2. The computing device ofclaim 1, wherein the MME is a control plane component that trackspositions of UEs in the cellular network.
 3. The computing device ofclaim 1, wherein the message from the UE is received over a low powerwide area network.
 4. The computing device of claim 3, wherein the lowpower wide area network is a narrow band wireless network.
 5. Thecomputing device of claim 1, wherein the actions comprise: receiving, atthe base station, an additional message from the UE; determining, at thebase station, that the additional message includes control plane data;generating, at the base station, an additional packet that includes atleast a portion of the additional message; based on determining that theadditional message includes control plane data, setting, at the basestation, an additional DSCP marking of the additional packet thatindicates the additional packet includes control plane data; andtransmitting, by the base station, the additional packet that includesthe additional DSCP marking that indicates the additional packetincludes control plane data and that indicates a priority of theadditional packet over the packet network to the MME of the cellularnetwork that authenticates UEs in the cellular network.
 6. The computingdevice of claim 1, wherein the actions comprise: receiving, at the basestation, an additional NAS message from the UE; determining, at the basestation, that a message type of the additional NAS message is an AttachRequest that indicates that the additional NAS message includes controlplane data; based on determining that the message type of the additionalNAS message is the Attach Request that indicates that the additional NASmessage includes control plane data, generating, at the base station, anadditional packet that includes at least a portion of the additional NASmessage; based on determining that the message type of the additionalNAS message is the Attach Request that indicates that the additional NASmessage includes control plane data, setting, at the base station, anadditional DSCP marking of the additional packet that indicates thepacket includes the portion of the additional NAS message that is theAttach Request that carries the control plane data; and transmitting, bythe base station, the additional packet that includes the DSCP markingthat indicates the additional packet includes the portion the additionalNAS message that is the Attach Request that caries the control planedata and that indicates a priority of the additional packet over thepacket network to the MME of the cellular network that authenticates UEsin the cellular network.
 7. A computer-implemented method, comprising:receiving, at a base station of a cellular network, a non-access stratum(NAS) message from a user equipment (UE); determining, at the basestation, that a message type of the NAS message is an evolved packetsystem session management (ESM) data transport that carries user planedata; based on determining that the message type of the NAS message isthe ESM data transport that carries user plane data, generating, at thebase station, a packet that includes at least a portion of the NASmessage; based on determining that the message type of the NAS messageis the ESM data transport that carries user plane data, setting, at thebase station, a Differentiated Services Code Point (DSCP) marking of thepacket that indicates the packet includes the portion of NAS messagethat is the ESM data transport that carries user plane data; andtransmitting, by the base station, the packet that includes the DSCPmarking that indicates the packet includes the portion of NAS messagethat is the ESM data transport that carries user plane data and thatindicates a priority of the packet over a packet network to a mobilitymanagement element (MME) of the cellular network that authenticates UEsin the cellular network.
 8. The computer-implemented method of claim 7,wherein the MME is a control plane component that tracks positions ofUEs in the cellular network.
 9. The computer-implemented method of claim7, wherein the message from the UE is received over a low power widearea network.
 10. The computer-implemented method of claim 9, whereinthe low power wide area network is a narrow band wireless network. 11.The computer-implemented method of claim 7, comprising: receiving, atthe base station, an additional message from the UE; determining, at thebase station, that the additional message includes control plane data;generating, at the base station, an additional packet that includes atleast a portion of the additional message; based on determining that theadditional message includes control plane data, setting, at the basestation, an additional DSCP marking of the additional packet thatindicates the additional packet includes control plane data; andtransmitting, by the base station, the additional packet that includesthe additional DSCP marking that indicates the additional packetincludes control plane data and that indicates a priority of theadditional packet over the packet network to the MME of the cellularnetwork that authenticates UEs in the cellular network.
 12. Thecomputer-implemented method of claim 7, comprising: receiving, at thebase station, an additional NAS message from the UE; determining, at thebase station, that a message type of the additional NAS message is anAttach Request that indicates that the additional NAS message includescontrol plane data; based on determining that the message type of theadditional NAS message is the Attach Request that indicates that theadditional NAS message includes control plane data, generating, at thebase station, an additional packet that includes at least a portion ofthe additional NAS message; based on determining that the message typeof the additional NAS message is the Attach Request that indicates thatthe additional NAS message includes control plane data, setting, at thebase station, an additional DSCP marking of the additional packet thatindicates the packet includes the portion of the additional NAS messagethat is the Attach Request that carries the control plane data; andtransmitting, by the base station, the additional packet that includesthe DSCP marking that indicates the additional packet includes theportion the additional NAS message that is the Attach Request thatcaries the control plane data and that indicates a priority of theadditional packet over the packet network to the MME of the cellularnetwork that authenticates UEs in the cellular network.
 13. A computingdevice comprising: one or more processors; and a non-transitorycomputer-readable medium storing a plurality of computer-executableinstructions that are executable by the one or more processors toperform a plurality of actions, the plurality of actions comprising:generating a non-access stratum (NAS) message for a user equipment (UE)at a mobility management element (MME) of a cellular network thatauthenticates UEs in the cellular network; determining that a messagetype of the NAS message is an evolved packet system session management(ESM) data transport that carries user plane data; based on determiningthat the message type of the NAS message is the ESM data transport thatcarries user plane data, generating a packet that includes at least aportion of the NAS message; based on determining that the message typeof the NAS message is the ESM data transport that carries user planedata, setting a Differentiated Services Code Point (DSCP) marking of thepacket that indicates the packet includes the portion of NAS messagethat is the ESM data transport that carries user plane data; andtransmitting the packet that includes the DSCP marking that indicatesthe packet includes the portion of NAS message that is the ESM datatransport that carries user plane data and that indicates a priority ofthe packet as user plane data over a packet network to a base station ofthe cellular network in transit to the UE.
 14. The computing device ofclaim 13, wherein the MME is a control plane component that trackspositions of UEs in the cellular network.
 15. The computing device ofclaim 13, wherein the message from the UE is received over a low powerwide area network.
 16. The computing device of claim 15, wherein the lowpower wide area network is a narrow band wireless network.
 17. Thecomputing device of claim 13, wherein the actions comprise: generatingan additional message for the UE at the MME; determining that a messagetype of the additional message includes control plane data; based ondetermining that the message type of the additional message includescontrol plane data, generating an additional packet that includes atleast a portion of the additional message; based on determining that themessage type of the additional message includes control plane data,setting an additional DSCP marking of the additional packet thatindicates that the additional packet includes control plane data; andtransmitting the additional packet that includes the additional DSCPmarking that indicates the additional packet includes control plane dataand that indicates a priority of the additional packet over the packetnetwork to a base station of the cellular network in transit to the UE.18. The computing device of claim 13, wherein the actions comprise:generating an additional NAS message for the UE at the MME; determiningthat a message type of the additional NAS message is an Attach Requestthat indicates that the additional NAS message includes control planedata; based on determining that the message type of the additional NASmessage is an Attach Request that indicates that the additional NASmessage includes control plane data, generating an additional packetthat includes at least a portion of the additional NAS message; based ondetermining that the message type of the additional NAS message is anAttach Request that indicates that the additional NAS message includescontrol plane data, setting an additional DSCP marking of the additionalpacket that indicates that the additional packet includes control planedata; and transmitting the additional packet that includes theadditional DSCP marking that indicates the additional packet includescontrol plane data and that indicates a priority of the additionalpacket over the packet network to the MME of the cellular network thatauthenticates UEs in the cellular network.